Distributed multimedia system for IP networks

ABSTRACT

A method, system, and computer-readable media are provided for facilitating communication of multimedia data across a distributed network. When the invention is employed for facilitating intra-communication between mobile network carriers, the invention can be configured to utilize a plurality of distribution sites. A first distribution site of a sender can receive an item of multimedia data and an identifier from a sender. The first distribution site may then transmit the identifier to a look-up server in order for the look-up server to identify the location of a recipient&#39;s distribution site. Once the look-up server identifies the recipient&#39;s distribution site for the first distribution site, the first distribution site can transmit the multimedia data to the recipient&#39;s distribution site.

PRIORITY

This application is a continuation of U.S. Ser. No. 11/466,513, entitled“Distributed Multimedia System for IP Networks,” filed 23 Aug. 2006,which is hereby incorporated by reference in its entirety.

CROSS-REFERENCE TO RELATED APPLICATIONS

Not applicable.

STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT

Not applicable.

BACKGROUND

It has become a growing trend for people to send a variety of differenttypes of multimedia content to one another through the use of theInternet. Users of mobile devices, such as cellular phones, areincreasingly sending multimedia data to other users of mobile devices.Such multimedia data may include, for example, voice messages, textmessages, both motion and still video content, and music content. Withthe growing number of mobile network subscribers, the processing of suchmultimedia data has become an ever increasing challenge.

Conventionally, mobile network service carriers process multimedia datatransmitted by their subscribers at one centralized location. However,this may require constant maintenance and a large amount facilities interms of floor space, power and cooling at these sites. There is a needto have a true multimedia platform or an integrated multimedia platformthat is distributable. Current standards do not provide a way in whichcarriers can distribute themselves to multiple sites for their ownneeds.

SUMMARY

The present invention is defined by the claims below. Embodiments of thepresent invention solve at least the above problems by providing asystem, method, and computer-readable media for, among other things,facilitating communication of multimedia data across a distributednetwork.

In a first aspect, a method for facilitating intra-communication ofmultimedia data within a carrier across a distributed network maycomprise receiving at least one item of multimedia data and anidentifier at a first distribution site. In such a method, the firstdistribution site may be associated with a sender and the identifier maybe associated with a recipient. The at least one item of multimedia dataand the identifier may be received using a first interface. The methodcan further comprise transmitting the identifier to a look-up server,wherein the identifier may be transmitted using a second interface.Moreover, the method can comprise receiving a reference to the locationof a second distribution site from the look-up server, wherein thesecond distribution site may be associated with the identifier.Additionally, the method can comprise transmitting the multimedia datato the second distribution site.

In another aspect, a system for facilitating intra-communication ofmultimedia data within a carrier across a distributed network maycomprise a first distribution site for receiving at least one item ofmultimedia data and an identifier. The first distribution site may beassociated with a sender and the identifier may be associated with arecipient. Additionally, the at least one item of multimedia data andthe identifier may be received using a first interface. The system mayfurther comprise a look-up server for receiving the identifier and usingthe identifier to determine a location of a distribution site for therecipient. The identifier may be received using a second interface.Moreover, the system may comprise a second distribution site forreceiving the at least one item of multimedia data from the firstdistribution site and for transmitting the at least one item ofmultimedia data to the recipient.

In yet another aspect, the invention discloses one or more tangiblecomputer-readable media having computer-useable instructions embodiedthereon for performing a method for facilitating communication ofmultimedia data across a distributed network, wherein the method maycomprise receiving at least one item of multimedia data and anidentifier at a first distribution site. In such a method, the firstdistribution site may be associated with a sender and the identifier maybe associated with a recipient. The at least one item of multimedia dataand the identifier may be received using a first interface. The methodcan further comprise transmitting the identifier to a look-up server,wherein the identifier may be transmitted using a second interface.Moreover, the method can comprise receiving a reference to the locationof a second distribution site from the look-up server, wherein thesecond distribution site may be associated with the identifier.Additionally, the method can comprise transmitting the multimedia datato the second distribution site.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

Illustrative embodiments of the present invention are described indetail below with reference to the attached drawing figures, which areincorporated by reference herein and wherein:

FIG. 1 illustrates an embodiment of a system for implementing theinvention.

FIG. 2 illustrates an embodiment of a method for facilitatingcommunication of multimedia data across a distributed network for asender that is a carrier subscriber.

FIG. 3 illustrates an embodiment of a method for facilitatingcommunication of multimedia data across a distributed network for asender that is a non-carrier subscriber.

FIG. 4 illustrates an embodiment of a detailed representation of amessaging component.

DETAILED DESCRIPTION

Embodiments of the present invention provide systems and methods forperforming a method for facilitating communication of multimedia dataacross a distributed network. The present invention provides the abilityto consolidate multimedia functions at multiple sites and for them toscale to a greater size than prior art. The present invention may be IPbased and can support legacy TDM transport as required. The ability todistribute increases the availability and scalability of the inventionwhile allowing for a consumer to be served by numerous applications at asingle site. This can have the benefit of providing lower latency andmay require less resources in terms of common application elements likeGroup Lists, Contact (Address Book) and Content. These solutions maysupport both landline and wireless devices with complete support forintra and inter-carrier communications.

ACRONYMS AND SHORTHAND NOTATIONS

Throughout the description of the present invention, several acronymsand shorthand notations are used to aid the understanding of certainconcepts pertaining to the associated system and services. Theseacronyms and shorthand notations are solely intended for the purpose ofproviding an easy methodology of communicating the ideas expressedherein and are in no way meant to limit the scope of the presentinvention. The following is a list of these acronyms:

MM Multimedia message MMS Multimedia service MMSC (Multimedia MessagingService Center) MMSC can be a store-and-forward method of transmittinggraphics, video clips, sound files and short text messages over wirelessnetworks using, for example, the WAP protocol. Carriers may deployservers, MMSCs, to implement the offerings on their systems. MMS mayalso support e-mail addressing, so the device can send e-mails directlyto an e-mail address. A common use of MMS is for communication betweenmobile phones. DNS (Domain Name System) DNS may be a mechanism used inthe Internet and on private Intranets for translating names of hostcomputers into addresses. When using a domain name, a DNS service cantranslate the name into the corresponding IP address. For example, thedomain name www.example.com may translate to 198.105.232.4 ENUM(Electronic Numbering - RFC 2916) ENUM is the Internet Engineering TaskForce (IETF) protocol that can assist in the convergence of the PublicSwitched Telephone Network (PSTN) and the IP network; it is the mappingof a telephone number from the PSTN to Internet services - a telephonenumber can be inputted, and an URL can be outputted. ENUM was developedas a solution to the question of how to find services on the Internetusing only a telephone number, and how telephones, which have an inputmechanism limited to twelve keys on a keypad, can be used to accessInternet services. ESMTP (Enhanced Simple Mail Transfer Protocol) ESMTPspecifies extensions to the original protocol for sending e-mail thatsupports graphics, audio and video files, and text in various nationallanguages. The original Internet protocols for sending e-mail aredescribed in Request for Comments (RFC) 822, Standard for the Format ofARPA Internet Text Messages, and in RFC 821, Simple Mail TransferProtocol (SMTP). As users began to want to attach various kinds of filesto e-mail, the need for additional capabilities arose and resulted inRFC 1869, Extended Simple Mail Transfer Protocol. ESMTP provides thecapability for a client e-mail program to ask a server e-mail programwhich capabilities it supports and then communicate accordingly.Currently, a lot of commercial e-mail servers and clients support ESMTP.IMP (IP Messaging Platform) IMP is a non/near-real time, IP-based,message delivery system allowing subscribers to view, edit, send,respond to, and receive messages which may include one or more objectsof various types. Defined objects include text, images, video, audio,music, files or applications. The IMP components which make up thesupporting platforms, sub-platforms, and supporting elements (to includethird party vendors) that support the defined product set consisting ofMail (Email & Short Mail), Picture/Video Mail, Text Messaging (SMS &Short Codes), Instant Messaging, Chat, Business Connection, Blackberry,PTT services, and Voice Mail. MM1 The MM1 interface allows interactionsbetween the MMS client in the device and the MMSC. 3GPP2 has defined thefunctional requirements of this interface. MM2 The MM2 interface is theinterface between two internal elements composing the MMSC: the MMSserver and relay. Most commercial solutions offer a combined relay andserver in the form of an MMSC. Consequently, the interface between therelay and server is developed in a proprietary fashion. MM3 The MM3interface is the interface between the MMSC and external servers.Transactions invoked over this interface allow exchange of messagesbetween the MMSCs and external servers such as e- mail or SMSC. Thisinterface is typically based on IP-based e-mail protocols. MM4 The MM4interface is the interface bridging two MMSCs. The interface is used toexchange multimedia messages between distinct mobile networkenvironments. Transactions invoked over this interface are carried outover the Simple Mail Transfer Protocol (SMTP). MM5 The MM5 interfaceenables interactions between the MMS and other network elements like theHome Location Register (HLR) or Domain Name Server (DNS). MM6 The MM6interface allows interactions between the MMSC and user databases (e.g.LDAP). This interface has not been standardized. MM7 The MM7 interfacefits between the MMSC and Value-Added Service (VAS) applications. Thisinterface allows a VAS application to request services from the MMSC(message submission, etc.) and to obtain messages from remote MMSclients. MM8 The MM8 interface enables interactions between the MMSC anda post-processing billing system. This interface hasn't beenstandardized. MM9 The MM9 interface enables interactions between theMMSC and an online charging system. With this interface, the MMSC cancheck whether prepaid customers have sufficient funds for services intheir account. This interface has not been standardized yet. MM10 TheMM10 interface allows interactions between the MMSC and a platformimplementing a Messaging Service Control Function (MSCF). The MMSCrequests the MSCF to execute some message- specific service logic thatmay influence addressing, routing and charging of multimedia messages;the MSCF can also access rights for users. This interface is in theprocess of being standardized, but no standard technical realization isavailable yet.

Further, various technical terms are used throughout this description. Adefinition of such terms can be found in Newton's Telecom Dictionary byH. Newton, 21^(st) Edition (2005). These definitions are intended toprovide a clearer understanding of the ideas disclosed herein but arenot intended to limit the scope of the present invention. Thedefinitions and terms should be interpreted broadly and liberally to theextent allowed the meaning of the words offered in the above-citedreference.

As one skilled in the art will appreciate, embodiments of the presentinvention may be embodied as, among other things: a method, system, orcomputer-program product. Accordingly, the embodiments may take the formof a hardware embodiment, a software embodiment, or an embodimentcombining software and hardware. In one embodiment, the presentinvention takes the form of a computer-program product that includescomputer-useable instructions embodied on one or more computer-readablemedia.

Computer-readable media include both volatile and nonvolatile media,removable and nonremovable media, and contemplates media readable by adatabase, a switch, and various other network devices. Network switches,routers, and related components are conventional in nature, as are meansof communicating with the same. By way of example, and not limitation,computer-readable media comprise computer-storage media andcommunications media.

Computer-storage media, or machine-readable media, include mediaimplemented in any method or technology for storing information.Examples of stored information include computer-useable instructions,data structures, program modules, and other data representations.Computer-storage media include, but are not limited to RAM, ROM, EEPROM,flash memory or other memory technology, CD-ROM, digital versatile discs(DVD), holographic media or other optical disc storage, magneticcassettes, magnetic tape, magnetic disk storage, and other magneticstorage devices. These memory components can store data momentarily,temporarily, or permanently.

Communications media typically store computer-useableinstructions—including data structures and program modules—in amodulated data signal. The term “modulated data signal” refers to apropagated signal that has one or more of its characteristics set orchanged to encode information in the signal. An exemplary modulated datasignal includes a carrier wave or other transport mechanism.Communications media include any information-delivery media. By way ofexample but not limitation, communications media include wired media,such as a wired network or direct-wired connection, and wireless mediasuch as acoustic, infrared, radio, microwave, spread-spectrum, and otherwireless media technologies. Combinations of the above are includedwithin the scope of computer-readable media.

FIG. 1 illustrates an embodiment of a system for implementing theinvention. The system may include client 102, distribution sites 104 and106, look-up server 108, and public traffic site 116. Client 102 may beor can include a desktop or laptop computer, a network-enabled cellulartelephone (with or without media capturing/playback capabilities),wireless email client, or other client, machine or device to performvarious tasks including Web browsing, search, electronic mail (email)and other tasks, applications and functions. Client 102 may additionallybe any portable media device such as digital still camera devices,digital video cameras (with or without still image capturefunctionality), media players such as personal music players andpersonal video players, and any other portable media device. In anembodiment, client 102 may also be a server such as a workstationrunning the Microsoft Windows®, MacOS™, Unix, Linux, Xenix, IBM AIX™,Hewlett-Packard UX™, Novell Netware™, Sun Microsystems Solaris™, OS/2™,BeOS™, Mach, Apache, OpenStep™ or other operating system or platform.

Distribution sites 104 and 106, look-up server 108, and public trafficsite 116 may be or can include a server such as a workstation runningthe Microsoft Windows®, MacOS™, Unix, Linux, Xenix, IBM AIX™,Hewlett-Packard UX™, Novell Netware™, Sun Microsystems Solaris™, OS/2™,BeOS™, Mach, Apache, OpenStep™ or other operating system or platform.

Look-up server 108 may be configured include a database that storesidentifiers with corresponding references to locations of otherdistribution sites. In an embodiment, the database may store identifierssuch as phone numbers of mobiles devices with references tocorresponding locations of each mobile devices' designated distributionsite. In such an embodiment, the reference of the location may be adomain name or URL of the mobile device's designated distribution site.In an embodiment, look-up server 108 may be an ENUM.

Distribution sites 104 and 106 may be utilized to push multimediacontent to a plurality of mobile network carrier subscribers. Inembodiments, there may be a multitude of distribution sites that areassigned to different mobile network carrier subscribers that are indifferent geographical locations. For example, a there could be adistribution site assigned to mobile network subscribers of a particularcarrier for each state within the United States. However, the inventionis not limited to such an example as any type of grouping of mobilenetwork subscribers of certain carriers within geographical locationscan be realized with the present invention. In an embodiment,distribution sites 104 and 106 may be MMSCs. Distribution sites 104 and106 may additionally include messaging components 112 and 114respectively. Messaging components 112 and 114 may be IP-based messagedelivery systems within the distribution sites that can allow users toview, edit, send, respond to, and receive multimedia messages which mayinclude one or more objects of various types. In an embodiment,messaging components 112 and 114 may be IMPs. In an embodiment,distribution sites 104 and 106 may belong to the same carrier. In otherembodiments, distribution sites 104 and 106 belong to differentcarriers.

Public traffic site 116 may be utilized to push multimedia data receivedfrom non-mobile network carrier subscribers to mobile network carriersubscribers. In an embodiment, public traffic site 116 may be acollection of one or more MMSCs. In an embodiment, public traffic site116 may also include relay 118. Relay 118 may be utilized to communicatewith an external server such as look-up server 108 through an interface.

Client 102, distribution sites 104 and 106, look-up server 108, andpublic traffic site 116 can each include a communication interface. Thecommunication interface may be an interface that can allow each deviceto be directly connected to any other device or allows each device to beconnected to another device over network 110. Network 110 can include,for example, a local area network (LAN), a wide area network (WAN), orthe Internet. In an embodiment, a device can be connected to anotherdevice via a wireless interface.

FIG. 2 illustrates an embodiment of a method for facilitatingcommunication of multimedia data across a distributed network for asender that is a carrier subscriber. In an embodiment, a carrier can bea mobile network service provider. In such an embodiment, differentcarriers may include, for example, Sprint, Verizon, Cingular, T-Mobile,etc. At operation 202, an item of multimedia data and an identifier arereceived at a sender's distribution site. The multimedia data andidentifier may be received through a first interface. In an embodiment,the first interface may be a MM1 interface. Multimedia data may includeany type of text, images, video, audio, or music content. In anembodiment, the identifier can be any type of reference to a recipient'sclient device. In an embodiment, the such a identifier can be the phonenumber of the recipient's mobile device.

At operation 204, the identifier may be transmitted to a look-up server.The sender's distribution site may communicate with the look-up serverthrough a second interface. In an embodiment, the second interface maybe a MM4 interface. In an embodiment, the look-up server may be an ENUM.Once the identifier is transmitted to the look-up server, the look-upserver may search its database to determine the recipient's distributionsite corresponding to the transmitted identifier. A reference to thelocation of the recipient's distribution site is transmitted from thelook-up server, and at operation 206, the reference is received by thesender's distribution site. In an embodiment, the reference of thelocation may be a domain name or URL of the recipient's designateddistribution site.

With the reference, the sender's distribution site can determine whetherthe recipient's distribution site belongs to the same carrier or adifferent carrier as the sender's distribution site. At operation 208,the sender's distribution site may use the reference to determine if therecipient's distribution site belongs to the same carrier as thesender's distribution site. If the sender's and recipient's distributionsites belong to the same carrier, then the sender's distribution sitecan use the reference to determine the location of the recipient'sdistribution site. Once the location has been determined, the sender'sdistribution site can contact the recipient's distribution site, and, atoperation 212, may transmit the multimedia data to the recipient'sdistribution site. The multimedia data can be transmitted from thesender's distribution site to the recipient's distribution site throughan interface. In an embodiment, such an interface may be a MM3interface. Additionally, in another embodiment, the multimedia data maybe transmitted using ESMTP. Once the multimedia data is received, therecipient's distribution site can then send the multimedia content tothe recipient's client device.

If, however, the sender's and recipient's distribution sites do notbelong to the same carrier, at operation 210, the sender's distributionsite contacts a Tier-1 service in order to identify the carrier thatcorresponds to the reference. Once the Tier-1 service identifies thecarrier, at operation 214, the sender's distribution site can contactthe corresponding carrier. At operation 212, the sender's distributionsite can transmit the multimedia data to the recipient's distributionsite of the other carrier that corresponds to the reference. Themultimedia data can be transmitted from the sender's distribution siteto the recipient's distribution site through an interface. In anembodiment, such an interface may be a MM3 interface. Additionally, inanother embodiment, the multimedia data may be transmitted using ESMTP.Once the multimedia data is received, the recipient's distribution sitemay then proceed to transmit the multimedia data to the recipient'sclient device.

FIG. 3 illustrates an embodiment of a method for facilitatingcommunication of multimedia data across a distributed network for asender that is a non-carrier subscriber. A non-carrier subscriber sendercan be any user of a client device who wishes to transmit multimediadata over a network, the Internet for example, wherein the sender'sclient device is not a part of a mobile network service provider. Atoperation 302, an item of multimedia data and an identifier is receivedat a public traffic site. In an embodiment, the identifier can be anytype of reference to a recipient's client device. In an embodiment, thesuch a reference can be the phone number of the recipient's mobiledevice. At operation 304, the identifier is transmitted to a look-upserver. In an embodiment, the look-up server may be an ENUM. The publictraffic site may communicate with the look-up server through aninterface. In an embodiment, the interface may be a MM4 interface.

Once the identifier is transmitted to the look-up server, the look-upserver may search its database to determine the recipient's distributionsite corresponding to the transmitted identifier. At operation 306, areference to the location of the recipient's distribution site isreceived by the public traffic site from the look-up server. In anembodiment, the reference of the location may be a domain name or URL ofthe recipient's designated distribution site.

With the reference, the public traffic site can determine therecipient's designated distribution site. At operation 308, the publictraffic site may transmit the multimedia data to the recipient'sdistribution site. The multimedia data can be transmitted from thepublic traffic site to the recipient's distribution site through aninterface. In an embodiment, such an interface may be a MM3 interface.Additionally, in another embodiment, the multimedia data may betransmitted using ESMTP. Once the multimedia data is received, therecipient's distribution site can then send the multimedia content tothe recipient's client device.

FIG. 4 illustrates an embodiment of a detailed representation of amessaging component 402. Messaging component 402 may include a MMSrelay/server component 404. In an embodiment, the relay may beconfigured to receive all the traffic sent to the messaging component402. The relay can determine whether to forward the traffic or to storethe traffic locally. FIG. 4 further illustrates an embodiment of how themessaging component communicates with various components throughinterfaces MM1-MM10 as defined above, wherein interfaces MM1-MM10 are apart of the 3GPP2 standard. Moreover, FIG. 4 illustrates that theinvention can be configured to service any type of carrier provider orthird-party server, for either intra or inter-carrier communication,using the MM3 and MM4 interfaces.

Many different arrangements of the various components depicted, as wellas components not shown, are possible without departing from the spiritand scope of the present invention. Embodiments of the present inventionhave been described with the intent to be illustrative rather thanrestrictive. Alternative embodiments will become apparent to thoseskilled in the art that do not depart from its scope. A skilled artisanmay develop alternative means of implementing the aforementionedimprovements without departing from the scope of the present invention.

It will be understood that certain features and subcombinations are ofutility and may be employed without reference to other features andsubcombinations and are contemplated within the scope of the claims. Notall steps listed in the various figures need be carried out in thespecific order described.

The invention claimed is:
 1. A method for facilitating communication ofmultimedia data across a distributed network, the method comprising:receiving at least one item of multimedia data and an identifier at apublic traffic site comprising a first communication interface, theidentifier being associated with a recipient, the public traffic sitecomprising a plurality of Multimedia Messaging Service Centers (MMSC)that form a geographically distributed multimedia processing platform inthe distributed network, and the at least one item of multimedia dataand the identifier received at the first communication interface;transmitting the identifier to a look-up server comprising a secondcommunication interface; receiving a reference to a location of adistribution site from the look-up server, the distribution sitecomprising a third communication interface and associated with theidentifier of the recipient, wherein the reference is at least one of adomain name and a Universal Resource Locator (URL) of the distributionsite; and determining whether the public traffic site and thedistribution site associated with the recipient belong to a samecarrier, wherein: when the public traffic site belongs to the samecarrier as the distribution site associated with the recipient,transmitting the at least one item of multimedia data to thedistribution site by transmitting the at least one item of multimediadata from the first communication interface to the third communicationinterface using the same carrier, and when the public traffic sitebelongs to a different carrier than the distribution site, which isassociated with a distribution site carrier, communicating with thelook-up server to identify the distribution site carrier for therecipient, contacting the distribution site carrier, and transmitting,via the distribution site carrier, the at least one item of multimediadata to the distribution site, wherein the distribution site isconfigured to push the at least one item of multimedia data to therecipient.
 2. The method of claim 1, wherein the recipient is a mobiledevice.
 3. The method of claim 2, wherein the identifier is a phonenumber of the mobile device.
 4. The method of claim 1, wherein at leastone of the first, second, and third communication interfaces is an MM4interface conforming to a version of the 3GPP2 standard.
 5. The methodof claim 1, wherein the distribution site transmits the at least oneitem of multimedia data to the recipient.
 6. The method of claim 1,further comprising receiving the identifier from a foreign networkcarrier at the public traffic site, wherein the recipient is asubscriber of a home network carrier and the public traffic site is asystem of the home network carrier.
 7. The method of claim 1, whereinthe distribution site is one of a plurality of distribution sites of ahome network carrier, each of which is geographically associated with arespective one or more subscribers of the home network carrier.